Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 92930b535d157971743f0c5b2a9fe8d1f7380de40efd616fcbea76018a425951

Tx prefix hash: e6603255f6330f702f1abd430d637c89a4c1d368447ece2f90c2323f480d557e
Tx public key: 20d04483d1af862c455eb42770b9700b2e7d747baa4a3690aa7006f52c739c03
Timestamp: 1701612525 Timestamp [UCT]: 2023-12-03 14:08:45 Age [y:d:h:m:s]: 01:129:18:34:52
Block: 905112 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 353909 RingCT/type: yes/0
Extra: 0120d04483d1af862c455eb42770b9700b2e7d747baa4a3690aa7006f52c739c0302110000000375e3f0e9000000000000000000

1 output(s) for total of 0.615160144000 dcy

stealth address amount amount idx
00: 6de9d277dafef2536e077569ea55df9167c8259e803e49c5d39819da15fdd821 0.615160144000 1361983 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": 905122, "vin": [ { "gen": { "height": 905112 } } ], "vout": [ { "amount": 615160144, "target": { "key": "6de9d277dafef2536e077569ea55df9167c8259e803e49c5d39819da15fdd821" } } ], "extra": [ 1, 32, 208, 68, 131, 209, 175, 134, 44, 69, 94, 180, 39, 112, 185, 112, 11, 46, 125, 116, 123, 170, 74, 54, 144, 170, 112, 6, 245, 44, 115, 156, 3, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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