Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 243d22c38322311fca7b16074cdb3f8dc3ee1c7f82e32ad61af10cf8bef51eab

Tx prefix hash: 505170b1d5e937134a98e8a52eeba37157244b4e650ddb74481176367b4f0d93
Tx public key: 6bc462ec530fc6ee29404e4c694bf4d683153c12f971f4e91c5de4fa1c3bc8ed
Timestamp: 1658166057 Timestamp [UCT]: 2022-07-18 17:40:57 Age [y:d:h:m:s]: 02:176:06:00:00
Block: 546573 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 647358 RingCT/type: yes/0
Extra: 016bc462ec530fc6ee29404e4c694bf4d683153c12f971f4e91c5de4fa1c3bc8ed02110000000133af99f4000000000000000000

1 output(s) for total of 9.483680077000 dcy

stealth address amount amount idx
00: 58bc2fde57b205253eab85f89f2e87dc43235c1945a00b2f47068bca5110aea1 9.483680077000 977604 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": 546583, "vin": [ { "gen": { "height": 546573 } } ], "vout": [ { "amount": 9483680077, "target": { "key": "58bc2fde57b205253eab85f89f2e87dc43235c1945a00b2f47068bca5110aea1" } } ], "extra": [ 1, 107, 196, 98, 236, 83, 15, 198, 238, 41, 64, 78, 76, 105, 75, 244, 214, 131, 21, 60, 18, 249, 113, 244, 233, 28, 93, 228, 250, 28, 59, 200, 237, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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