Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d56b518557772ba7154000078b88e4fdd2b2ad6c5af2d1e396851a20ee8b3c60

Tx prefix hash: 2118ae24064f8cc6d68e9ff2abafbec7d95e8333cb7d5e1c5e21e8741211c5f9
Tx public key: c87258a1a1f517e8373304b74c5d687330630c20c4a08985c2ce3045eb9db08e
Timestamp: 1715087442 Timestamp [UCT]: 2024-05-07 13:10:42 Age [y:d:h:m:s]: 00:239:01:42:35
Block: 1016834 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 171108 RingCT/type: yes/0
Extra: 01c87258a1a1f517e8373304b74c5d687330630c20c4a08985c2ce3045eb9db08e02110000000c0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 770d029d1c032fbd87058bd49bea3709e1ff580f45326930bc633eb3b128dd85 0.600000000000 1480533 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": 1016844, "vin": [ { "gen": { "height": 1016834 } } ], "vout": [ { "amount": 600000000, "target": { "key": "770d029d1c032fbd87058bd49bea3709e1ff580f45326930bc633eb3b128dd85" } } ], "extra": [ 1, 200, 114, 88, 161, 161, 245, 23, 232, 55, 51, 4, 183, 76, 93, 104, 115, 48, 99, 12, 32, 196, 160, 137, 133, 194, 206, 48, 69, 235, 157, 176, 142, 2, 17, 0, 0, 0, 12, 0, 17, 5, 91, 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