Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 831556ba7a27441972791f15a485c0cea178021a21c8c86ceff150077b6ef11d

Tx prefix hash: eb85201452ab15328ed3f84bad22e5e0e14e64e9c36e285a73e4edccd3c4980e
Tx public key: fb29b4e6d6b2e8ac33af8a5d320ed5499134432e5ca728e3f9c9cc01ed516853
Timestamp: 1730329312 Timestamp [UCT]: 2024-10-30 23:01:52 Age [y:d:h:m:s]: 00:024:08:24:16
Block: 1143107 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 17428 RingCT/type: yes/0
Extra: 01fb29b4e6d6b2e8ac33af8a5d320ed5499134432e5ca728e3f9c9cc01ed516853021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cd70a6b13800b7c5a63a9ec3100c4b12970711cca5a6f258feeaca7c3a3ab4c8 0.600000000000 1626970 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": 1143117, "vin": [ { "gen": { "height": 1143107 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cd70a6b13800b7c5a63a9ec3100c4b12970711cca5a6f258feeaca7c3a3ab4c8" } } ], "extra": [ 1, 251, 41, 180, 230, 214, 178, 232, 172, 51, 175, 138, 93, 50, 14, 213, 73, 145, 52, 67, 46, 92, 167, 40, 227, 249, 201, 204, 1, 237, 81, 104, 83, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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