Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f96c74eb12a450e67866d67cfc30ecf36ede9c29a208fdfb97d8ed7e67e4979d

Tx prefix hash: 4b9ab334e77975ec327031dc501fc9652986ee48e4e34041ea843f652cdca89a
Tx public key: 280a24288c68f225af654883d9f4e6991ab7f4561a8f4b80b1ee4ce8e22020e1
Timestamp: 1774050590 Timestamp [UTC]: 2026-03-20 23:49:50 Age [y:d:h:m:s]: 00:239:20:20:11
Block: 1502246 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176885 RingCT/type: yes/0
Extra: 01280a24288c68f225af654883d9f4e6991ab7f4561a8f4b80b1ee4ce8e22020e1021100000002f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 2c8876d16fcca5af5cc10dd0d5bb4cd5cad1d6af0563311b3f332cbdad91aed6 0.000600000000 1991940 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": 1502256, "vin": [ { "gen": { "height": 1502246 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2c8876d16fcca5af5cc10dd0d5bb4cd5cad1d6af0563311b3f332cbdad91aed6" } } ], "extra": [ 1, 40, 10, 36, 40, 140, 104, 242, 37, 175, 101, 72, 131, 217, 244, 230, 153, 26, 183, 244, 86, 26, 143, 75, 128, 177, 238, 76, 232, 226, 32, 32, 225, 2, 17, 0, 0, 0, 2, 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: