Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9080b853137313e7f7d1b8c2fc870eae87f4cd1112f1c992ca8c3d82d1f7b806

Tx prefix hash: 037d303d7373bb2a07c2a3fabf80b65e5e633d51257342b01d0fdf9c0cf4eb75
Tx public key: b3f6f04c5de59025f98e4f0049ce03b715fe25fbdd0c8e183135db4ea2536dad
Timestamp: 1734099840 Timestamp [UTC]: 2024-12-13 14:24:00 Age [y:d:h:m:s]: 01:148:07:43:12
Block: 1174362 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 357022 RingCT/type: yes/0
Extra: 01b3f6f04c5de59025f98e4f0049ce03b715fe25fbdd0c8e183135db4ea2536dad021100000001007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: cda5a47cc09799de75eb73c480c7c43b459fd8130cc4971df16270101b4acaa7 0.000600000000 1660505 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": 1174372, "vin": [ { "gen": { "height": 1174362 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cda5a47cc09799de75eb73c480c7c43b459fd8130cc4971df16270101b4acaa7" } } ], "extra": [ 1, 179, 246, 240, 76, 93, 229, 144, 37, 249, 142, 79, 0, 73, 206, 3, 183, 21, 254, 37, 251, 221, 12, 142, 24, 49, 53, 219, 78, 162, 83, 109, 173, 2, 17, 0, 0, 0, 1, 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: