Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 85f4a18c1b50459fe4ce02f67aa4eb04c4211cc9ea3182d4a774936e67aad356

Tx prefix hash: ddcb37ecc4448fd38fa6b7a6fc10762ebcb7dda04aaf162383d032d9dd43e065
Tx public key: b33bf3f04dd5cc47bda0180f8c92a5c199fdd82b1e76a1cb533f616319079947
Timestamp: 1717393707 Timestamp [UCT]: 2024-06-03 05:48:27 Age [y:d:h:m:s]: 00:289:16:26:33
Block: 1035965 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207032 RingCT/type: yes/0
Extra: 01b33bf3f04dd5cc47bda0180f8c92a5c199fdd82b1e76a1cb533f616319079947021100000002162613aa000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ebf458922ac0fc42d3d9968c8da7321c0cba82150020f51d2c1b82bfcceb89c3 0.600000000000 1504490 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": 1035975, "vin": [ { "gen": { "height": 1035965 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ebf458922ac0fc42d3d9968c8da7321c0cba82150020f51d2c1b82bfcceb89c3" } } ], "extra": [ 1, 179, 59, 243, 240, 77, 213, 204, 71, 189, 160, 24, 15, 140, 146, 165, 193, 153, 253, 216, 43, 30, 118, 161, 203, 83, 63, 97, 99, 25, 7, 153, 71, 2, 17, 0, 0, 0, 2, 22, 38, 19, 170, 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