Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf475647f3289aebcc553d159615293e0a4c6e5b92f578b824fb15c7f2fa8e75

Tx prefix hash: 9e34e4832197091c1203b68705620e2c9bfdb1529b932cb420e2f6fccfc320cd
Tx public key: 6db2f8b4e7e6b66da5b9eed4eec39dff46eacd5a2838d4fe02b26ca2dc3b12d9
Timestamp: 1717937386 Timestamp [UCT]: 2024-06-09 12:49:46 Age [y:d:h:m:s]: 00:321:03:42:29
Block: 1040455 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 229534 RingCT/type: yes/0
Extra: 016db2f8b4e7e6b66da5b9eed4eec39dff46eacd5a2838d4fe02b26ca2dc3b12d90211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2e209cc606751fd5f03d8633ebfc8c9239c71a310822e69644439bbb781179f7 0.600000000000 1509112 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": 1040465, "vin": [ { "gen": { "height": 1040455 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2e209cc606751fd5f03d8633ebfc8c9239c71a310822e69644439bbb781179f7" } } ], "extra": [ 1, 109, 178, 248, 180, 231, 230, 182, 109, 165, 185, 238, 212, 238, 195, 157, 255, 70, 234, 205, 90, 40, 56, 212, 254, 2, 178, 108, 162, 220, 59, 18, 217, 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