Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 07d8a9c79384553a9fe4377d4a39488db5d6724c1843cf91e1eb77233bdf7b0f

Tx prefix hash: fa16da5dcca56af188046dd866e366ecb7e618d8dafdf8a274e36929c528831f
Tx public key: 929d2938b11b202a5e4a127754100435c29a0a79d2e8ea5a4436d4adf78e3318
Timestamp: 1729821640 Timestamp [UCT]: 2024-10-25 02:00:40 Age [y:d:h:m:s]: 00:030:01:48:11
Block: 1138948 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 21481 RingCT/type: yes/0
Extra: 01929d2938b11b202a5e4a127754100435c29a0a79d2e8ea5a4436d4adf78e33180211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b61deba76a41aac14ea68c01720b89c3f6ec01f4e1cddf726dcd1d50acd321dd 0.600000000000 1622691 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": 1138958, "vin": [ { "gen": { "height": 1138948 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b61deba76a41aac14ea68c01720b89c3f6ec01f4e1cddf726dcd1d50acd321dd" } } ], "extra": [ 1, 146, 157, 41, 56, 177, 27, 32, 42, 94, 74, 18, 119, 84, 16, 4, 53, 194, 154, 10, 121, 210, 232, 234, 90, 68, 54, 212, 173, 247, 142, 51, 24, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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