Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 303fc9261dd1abff5bcd7c0ae061df5dfbe31148411a73adac53badd13191e74

Tx prefix hash: 1b9cfeba03d13ba231e8c60e1fa70a9c05ca57b9d30a134cb46099ccf2b3f325
Tx public key: 0ac92f517fc354f6135466f2f2fa3a68431c3a4cb98349ed914496a5fe8987bc
Timestamp: 1703694369 Timestamp [UCT]: 2023-12-27 16:26:09 Age [y:d:h:m:s]: 01:112:17:48:10
Block: 922370 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 341704 RingCT/type: yes/0
Extra: 010ac92f517fc354f6135466f2f2fa3a68431c3a4cb98349ed914496a5fe8987bc0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 788afdc964918cc8c0978dfe3e8194e4531cf393826a4628f1f134bee82a79f8 0.600000000000 1380066 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": 922380, "vin": [ { "gen": { "height": 922370 } } ], "vout": [ { "amount": 600000000, "target": { "key": "788afdc964918cc8c0978dfe3e8194e4531cf393826a4628f1f134bee82a79f8" } } ], "extra": [ 1, 10, 201, 47, 81, 127, 195, 84, 246, 19, 84, 102, 242, 242, 250, 58, 104, 67, 28, 58, 76, 185, 131, 73, 237, 145, 68, 150, 165, 254, 137, 135, 188, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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