Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fe508fed9f1dcc840155f83ddffaee95441fd4feb8adc9cc5e0f237a7164bff9

Tx prefix hash: cc10ad1366d19d842fd6e41d59c1978e816d7177827904933d731f5b4f2d47ca
Tx public key: 301d23e98439d2606743460cc5af978023374dfbc6735daf01a41d00cab7c1d0
Timestamp: 1700857102 Timestamp [UCT]: 2023-11-24 20:18:22 Age [y:d:h:m:s]: 01:097:02:21:47
Block: 898854 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 330527 RingCT/type: yes/0
Extra: 01301d23e98439d2606743460cc5af978023374dfbc6735daf01a41d00cab7c1d0021100000003faf35c9c000000000000000000

1 output(s) for total of 0.645243370000 dcy

stealth address amount amount idx
00: 6c6a2a31b18d680e0b7bd66d24e6cc3ae0f0c656c7afab0414efc76176911b24 0.645243370000 1355291 of 0

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": 898864, "vin": [ { "gen": { "height": 898854 } } ], "vout": [ { "amount": 645243370, "target": { "key": "6c6a2a31b18d680e0b7bd66d24e6cc3ae0f0c656c7afab0414efc76176911b24" } } ], "extra": [ 1, 48, 29, 35, 233, 132, 57, 210, 96, 103, 67, 70, 12, 197, 175, 151, 128, 35, 55, 77, 251, 198, 115, 93, 175, 1, 164, 29, 0, 202, 183, 193, 208, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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