Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 247e210cb9e3ac9ad113e827942150410279f842966a4677d6e393528887bac5

Tx prefix hash: 9ed73675b2c1755d7c9e73c12b35780f45469bf9b2ddf01b7d6d915c69f145a2
Tx public key: aef0aa4a8190899b466e3f4149aa6ebc36f8f936e4285fc5645fba3e6d2c0129
Timestamp: 1731191556 Timestamp [UCT]: 2024-11-09 22:32:36 Age [y:d:h:m:s]: 01:001:17:06:58
Block: 1150257 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 259628 RingCT/type: yes/0
Extra: 01aef0aa4a8190899b466e3f4149aa6ebc36f8f936e4285fc5645fba3e6d2c0129021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 98119854cec3ca59761cfef6e243b881c6f849f032ec724e4cf929576eae3e52 0.600000000000 1635514 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": 1150267, "vin": [ { "gen": { "height": 1150257 } } ], "vout": [ { "amount": 600000000, "target": { "key": "98119854cec3ca59761cfef6e243b881c6f849f032ec724e4cf929576eae3e52" } } ], "extra": [ 1, 174, 240, 170, 74, 129, 144, 137, 155, 70, 110, 63, 65, 73, 170, 110, 188, 54, 248, 249, 54, 228, 40, 95, 197, 100, 95, 186, 62, 109, 44, 1, 41, 2, 17, 0, 0, 0, 2, 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