Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 21b47bd8944f53298d600ea37b962c85f18bb8de332e9dffe3ea6d0dbb1bce95

Tx prefix hash: f20ba10bd91c7faab331c7559ffffc6d4370aa8699b020b2e87d2c53bcf8b937
Tx public key: cf5fd2dac3a2f5cbdae86c54a5991f60f6408585735549af22e64b5b5c1e8b51
Timestamp: 1773563459 Timestamp [UTC]: 2026-03-15 08:30:59 Age [y:d:h:m:s]: 00:244:05:47:14
Block: 1498245 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179945 RingCT/type: yes/0
Extra: 01cf5fd2dac3a2f5cbdae86c54a5991f60f6408585735549af22e64b5b5c1e8b51021100000001f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 249ef88f727b9017a8997e8023463e44de898d3ffb491878e796050e6dc608a4 0.000600000000 1987891 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 dinastycoin-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": 1498255, "vin": [ { "gen": { "height": 1498245 } } ], "vout": [ { "amount": 600000000, "target": { "key": "249ef88f727b9017a8997e8023463e44de898d3ffb491878e796050e6dc608a4" } } ], "extra": [ 1, 207, 95, 210, 218, 195, 162, 245, 203, 218, 232, 108, 84, 165, 153, 31, 96, 246, 64, 133, 133, 115, 85, 73, 175, 34, 230, 75, 91, 92, 30, 139, 81, 2, 17, 0, 0, 0, 1, 241, 136, 200, 168, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: