Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f28f0f3737ea8766a2a7bb8635cdceacafaa3a90b9f6d471aa306132d3e734d

Tx prefix hash: 839a8e28045287c447f29042ef0b1b7a080be3a65cfea6ad984f4819334480cb
Tx public key: 188aa3b96838e85898f6345ea7d8a480bd7687902e053a7a9f1b9821cab9de73
Timestamp: 1730273603 Timestamp [UCT]: 2024-10-30 07:33:23 Age [y:d:h:m:s]: 00:083:23:20:55
Block: 1142659 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 60029 RingCT/type: yes/0
Extra: 01188aa3b96838e85898f6345ea7d8a480bd7687902e053a7a9f1b9821cab9de73021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3434465ce4629e8fc3b36b1e66de7e8dcd6e25745c7ed0a26892ddbdf240e228 0.600000000000 1626514 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": 1142669, "vin": [ { "gen": { "height": 1142659 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3434465ce4629e8fc3b36b1e66de7e8dcd6e25745c7ed0a26892ddbdf240e228" } } ], "extra": [ 1, 24, 138, 163, 185, 104, 56, 232, 88, 152, 246, 52, 94, 167, 216, 164, 128, 189, 118, 135, 144, 46, 5, 58, 122, 159, 27, 152, 33, 202, 185, 222, 115, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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