Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db6895187187cf8e58c26a800f5626da3286ae8501fa46290bcf723f91b07e52

Tx prefix hash: 2e0027a9ad7ed7193e151ca534a79f1e35b432f6347c89dafcbe4c5226b1c7be
Tx public key: 158dd976365f5f3aa59cd0d0cf8f2750ca31a83667e44cb503a951bd6b561736
Timestamp: 1727559607 Timestamp [UCT]: 2024-09-28 21:40:07 Age [y:d:h:m:s]: 00:167:03:21:23
Block: 1120232 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119269 RingCT/type: yes/0
Extra: 01158dd976365f5f3aa59cd0d0cf8f2750ca31a83667e44cb503a951bd6b561736021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0d35bd215b56f810eeb319f711f42bb2b80a9e7ccd4e9a8e664a4fdcb0ebdd10 0.600000000000 1602073 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": 1120242, "vin": [ { "gen": { "height": 1120232 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0d35bd215b56f810eeb319f711f42bb2b80a9e7ccd4e9a8e664a4fdcb0ebdd10" } } ], "extra": [ 1, 21, 141, 217, 118, 54, 95, 95, 58, 165, 156, 208, 208, 207, 143, 39, 80, 202, 49, 168, 54, 103, 228, 76, 181, 3, 169, 81, 189, 107, 86, 23, 54, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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