Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c2b3191cdb26a51d63d8ac7b9e955e824d95714c6294bbed42fbb3b2fca32157

Tx prefix hash: 17a8ad44f4de2873569cf7f11c89d5a89f191f59e819e0630f67ebe45d25618d
Tx public key: bf096841f81de1813cc6e7e84309198b99eefd7f9f34691ffd555604d72da0a6
Timestamp: 1738101650 Timestamp [UTC]: 2025-01-28 22:00:50 Age [y:d:h:m:s]: 01:103:07:48:04
Block: 1207205 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 324681 RingCT/type: yes/0
Extra: 01bf096841f81de1813cc6e7e84309198b99eefd7f9f34691ffd555604d72da0a602110000000b007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 1aa7778ac17a8558fc7871a2e848e10614738ce0737923fc47de6c21fdb16de1 0.000600000000 1693926 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": 1207215, "vin": [ { "gen": { "height": 1207205 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1aa7778ac17a8558fc7871a2e848e10614738ce0737923fc47de6c21fdb16de1" } } ], "extra": [ 1, 191, 9, 104, 65, 248, 29, 225, 129, 60, 198, 231, 232, 67, 9, 25, 139, 153, 238, 253, 127, 159, 52, 105, 31, 253, 85, 86, 4, 215, 45, 160, 166, 2, 17, 0, 0, 0, 11, 0, 127, 151, 138, 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: