Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 90982e9be48bbc689b9f0e4067c9577c42bad2e7c9ebd2cefd88c010d45adcfd

Tx prefix hash: 75ae91c806b09c4912333bd09885895e5cff2c225197337357e80dc7ebb65f5f
Tx public key: 72fc6ebb48d16eafb02b5ea588451ff2d7e867e4473930fbcc5faa317052d4c8
Timestamp: 1717020444 Timestamp [UCT]: 2024-05-29 22:07:24 Age [y:d:h:m:s]: 00:299:11:41:40
Block: 1032855 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214036 RingCT/type: yes/0
Extra: 0172fc6ebb48d16eafb02b5ea588451ff2d7e867e4473930fbcc5faa317052d4c802110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f3b59367b291df9d7a97b51c9a7cb47abbc23f3de82a12f286a5d668e18e171c 0.600000000000 1501310 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": 1032865, "vin": [ { "gen": { "height": 1032855 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f3b59367b291df9d7a97b51c9a7cb47abbc23f3de82a12f286a5d668e18e171c" } } ], "extra": [ 1, 114, 252, 110, 187, 72, 209, 110, 175, 176, 43, 94, 165, 136, 69, 31, 242, 215, 232, 103, 228, 71, 57, 48, 251, 204, 95, 170, 49, 112, 82, 212, 200, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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