Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 170bb46bf51021ce2c4c30a212a349a22947e359dfc3c64fa99c938bf28e0391

Tx prefix hash: 7ce2a9026a9ac4a307c14f8877975f12b7a2d9b1469d0550d2189c280e3e5dba
Tx public key: 24ccfc004c59b5be75e068310064d657b14dfbf2d92b4d68b5fde55c8d48c8b1
Timestamp: 1728599346 Timestamp [UCT]: 2024-10-10 22:29:06 Age [y:d:h:m:s]: 00:204:16:31:58
Block: 1128849 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 146088 RingCT/type: yes/0
Extra: 0124ccfc004c59b5be75e068310064d657b14dfbf2d92b4d68b5fde55c8d48c8b102110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 95784fc1c7611bcc8519fc504e830fcde42ab942974ff3d2776c183d3b25b0b8 0.600000000000 1611672 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": 1128859, "vin": [ { "gen": { "height": 1128849 } } ], "vout": [ { "amount": 600000000, "target": { "key": "95784fc1c7611bcc8519fc504e830fcde42ab942974ff3d2776c183d3b25b0b8" } } ], "extra": [ 1, 36, 204, 252, 0, 76, 89, 181, 190, 117, 224, 104, 49, 0, 100, 214, 87, 177, 77, 251, 242, 217, 43, 77, 104, 181, 253, 229, 92, 141, 72, 200, 177, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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