Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 21e1913a0e9480e7abb0178d43a24e595d832c9d38dde30a512a4790d55832fc

Tx prefix hash: 087eebaaab2834a03938cbd726e70a9c5bc884d7c846de277754bb2d009d62e6
Tx public key: 9a1aa38ae843c46d976505e0cd64b870902bd0fd88a625c1b44cccc28cf32a04
Timestamp: 1737475740 Timestamp [UCT]: 2025-01-21 16:09:00 Age [y:d:h:m:s]: 00:304:03:49:19
Block: 1202242 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214936 RingCT/type: yes/0
Extra: 019a1aa38ae843c46d976505e0cd64b870902bd0fd88a625c1b44cccc28cf32a04021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4db4ec22472298dc465bfd3ae2fb79b49baf57d57a1037280000c6876a3d1e04 0.600000000000 1688905 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": 1202252, "vin": [ { "gen": { "height": 1202242 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4db4ec22472298dc465bfd3ae2fb79b49baf57d57a1037280000c6876a3d1e04" } } ], "extra": [ 1, 154, 26, 163, 138, 232, 67, 196, 109, 151, 101, 5, 224, 205, 100, 184, 112, 144, 43, 208, 253, 136, 166, 37, 193, 180, 76, 204, 194, 140, 243, 42, 4, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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