Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fce5d173d8994eca60c1c146be4aed32eba4d3d9f085ca87b380181953ff7d23

Tx prefix hash: 591c4ee1c5fd362b02aaffd773f1599d176a846b419419c1a266f3f976c1c241
Tx public key: ab9e3c38f55b165372ffaa76f68e48cb5a02111905c5735005ecbc26a5a39526
Timestamp: 1716794187 Timestamp [UCT]: 2024-05-27 07:16:27 Age [y:d:h:m:s]: 00:314:11:20:42
Block: 1030992 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 224729 RingCT/type: yes/0
Extra: 01ab9e3c38f55b165372ffaa76f68e48cb5a02111905c5735005ecbc26a5a3952602110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 579dc370a01ebaf58e0c0ac7e4d5200d596c16efcd4f38d29e19036c84085d48 0.600000000000 1499325 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": 1031002, "vin": [ { "gen": { "height": 1030992 } } ], "vout": [ { "amount": 600000000, "target": { "key": "579dc370a01ebaf58e0c0ac7e4d5200d596c16efcd4f38d29e19036c84085d48" } } ], "extra": [ 1, 171, 158, 60, 56, 245, 91, 22, 83, 114, 255, 170, 118, 246, 142, 72, 203, 90, 2, 17, 25, 5, 197, 115, 80, 5, 236, 188, 38, 165, 163, 149, 38, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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