Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb657600186efb1b088089cefafb3223d9db228b1fe663e11319d16e12b5e564

Tx prefix hash: 96fe8e8b544d9efae3b84ebee98c0602952f9615e33075c4d544375cdbf93bd6
Tx public key: ce6518cf33e86beaee6b3fb79bb7953fb442b3ce32077ee49b0883a209b8b8c6
Timestamp: 1661212197 Timestamp [UCT]: 2022-08-22 23:49:57 Age [y:d:h:m:s]: 02:229:03:46:45
Block: 571704 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 685002 RingCT/type: yes/0
Extra: 01ce6518cf33e86beaee6b3fb79bb7953fb442b3ce32077ee49b0883a209b8b8c6021100000007e6d27f9c000000000000000000

1 output(s) for total of 7.829020367000 dcy

stealth address amount amount idx
00: c106f596f525738767d04a4acf35169dc031d8eaad9b8e9227a6867c722a0850 7.829020367000 1004928 of 0

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": 571714, "vin": [ { "gen": { "height": 571704 } } ], "vout": [ { "amount": 7829020367, "target": { "key": "c106f596f525738767d04a4acf35169dc031d8eaad9b8e9227a6867c722a0850" } } ], "extra": [ 1, 206, 101, 24, 207, 51, 232, 107, 234, 238, 107, 63, 183, 155, 183, 149, 63, 180, 66, 179, 206, 50, 7, 126, 228, 155, 8, 131, 162, 9, 184, 184, 198, 2, 17, 0, 0, 0, 7, 230, 210, 127, 156, 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