Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd1e91c8f8d5d4cef5fc1654f0a6fb711d1e941e8f33555bcf13771f496efeb9

Tx prefix hash: 30bfaf07af2295b14cf4dea8b926b88f93d9a2eb3d42129243610e2bb7456991
Tx public key: 7e8f3853a07597e1a61d2f92e15388109df7900305612c4e6ca0fb4ae427cb7e
Timestamp: 1730841703 Timestamp [UCT]: 2024-11-05 21:21:43 Age [y:d:h:m:s]: 00:151:09:52:26
Block: 1147339 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108052 RingCT/type: yes/0
Extra: 017e8f3853a07597e1a61d2f92e15388109df7900305612c4e6ca0fb4ae427cb7e0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c2ffa4c351e071d5a694e1b14649722de99c1d76b3eccc80e9fe4b1135152d7b 0.600000000000 1632034 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": 1147349, "vin": [ { "gen": { "height": 1147339 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c2ffa4c351e071d5a694e1b14649722de99c1d76b3eccc80e9fe4b1135152d7b" } } ], "extra": [ 1, 126, 143, 56, 83, 160, 117, 151, 225, 166, 29, 47, 146, 225, 83, 136, 16, 157, 247, 144, 3, 5, 97, 44, 78, 108, 160, 251, 74, 228, 39, 203, 126, 2, 17, 0, 0, 0, 1, 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