Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ce663431d1f6f38f222d9999721acb4149af95d8ec8cf0804e8eda6b89dd064

Tx prefix hash: c1312c79e8dbbc89374a15dae3be1057d72f1be5baa88cfa191dba70709fbf2b
Tx public key: 7b96f2c3c666d3206f9a298f33c0d918a1f0454a456740e8541b0ce29e0587b0
Timestamp: 1702634653 Timestamp [UCT]: 2023-12-15 10:04:13 Age [y:d:h:m:s]: 01:335:14:28:38
Block: 913585 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 498720 RingCT/type: yes/0
Extra: 017b96f2c3c666d3206f9a298f33c0d918a1f0454a456740e8541b0ce29e0587b002110000000175e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3f8ef018b1a54b5b045c391702fe1cad8974b79a2d9c2e94005497009852606c 0.600000000000 1370859 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": 913595, "vin": [ { "gen": { "height": 913585 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3f8ef018b1a54b5b045c391702fe1cad8974b79a2d9c2e94005497009852606c" } } ], "extra": [ 1, 123, 150, 242, 195, 198, 102, 211, 32, 111, 154, 41, 143, 51, 192, 217, 24, 161, 240, 69, 74, 69, 103, 64, 232, 84, 27, 12, 226, 158, 5, 135, 176, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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