Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 3e4c21a51981715c8018c0ce1a0faa58bcc054b7cf58ed62ac9ccdaa5159b5ba

Tx prefix hash: 8042fbcd0432f36974a16a9f80b1cfdd15e466dd4c292c52a77630e110dd26a0
Tx public key: 790298f7f58f54b70e03e8b899315b9bdd65dc25f45f81805994a449e5e938fd
Timestamp: 1728541534 Timestamp [UCT]: 2024-10-10 06:25:34 Age [y:d:h:m:s]: 00:161:16:22:50
Block: 1128369 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115356 RingCT/type: yes/0
Extra: 01790298f7f58f54b70e03e8b899315b9bdd65dc25f45f81805994a449e5e938fd02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 55828f1f93e7f570cf08e31393e38732c1a6e8927e62089f46985be7b93c2572 0.600000000000 1611186 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1128379, "vin": [ { "gen": { "height": 1128369 } } ], "vout": [ { "amount": 600000000, "target": { "key": "55828f1f93e7f570cf08e31393e38732c1a6e8927e62089f46985be7b93c2572" } } ], "extra": [ 1, 121, 2, 152, 247, 245, 143, 84, 183, 14, 3, 232, 184, 153, 49, 91, 155, 221, 101, 220, 37, 244, 95, 129, 128, 89, 148, 164, 73, 229, 233, 56, 253, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8