Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2b64ff8f0c5622178eec1f59170dc16aafec78ea2595623a75f043f584bd74a

Tx prefix hash: ce2fd14f0297f44ed3f0aff22682ce3254b93e7493aeeb688336a160b96f635a
Tx public key: 687ac945f653f9296b9181a356cd27dd3642131fbe713c9ac0b476f08628f4d5
Timestamp: 1741789343 Timestamp [UTC]: 2025-03-12 14:22:23 Age [y:d:h:m:s]: 01:245:13:43:27
Block: 1237744 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 439381 RingCT/type: yes/0
Extra: 01687ac945f653f9296b9181a356cd27dd3642131fbe713c9ac0b476f08628f4d5021100000006007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 74b344915c1aa4f4ec84cdc95ffb3eb77fa2dfd1869d62130efc23ae204e7cf6 0.000600000000 1724701 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": 1237754, "vin": [ { "gen": { "height": 1237744 } } ], "vout": [ { "amount": 600000000, "target": { "key": "74b344915c1aa4f4ec84cdc95ffb3eb77fa2dfd1869d62130efc23ae204e7cf6" } } ], "extra": [ 1, 104, 122, 201, 69, 246, 83, 249, 41, 107, 145, 129, 163, 86, 205, 39, 221, 54, 66, 19, 31, 190, 113, 60, 154, 192, 180, 118, 240, 134, 40, 244, 213, 2, 17, 0, 0, 0, 6, 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: