Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b7c8310a059d85669d0b0f08ba563eed9f0cf2eabace19be66fa23ea3e6ae9ad

Tx prefix hash: 0c83e32d2a0d9f5a8bd1595670605ef4d3d41d116fcd614cadbb8e6f1b8122d6
Tx public key: a007f674bea16c3a4d9d41739c774b0c063ff79b145d237ca82f58b727b699fd
Timestamp: 1765149144 Timestamp [UTC]: 2025-12-07 23:12:24 Age [y:d:h:m:s]: 00:343:08:58:27
Block: 1428737 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 250777 RingCT/type: yes/0
Extra: 01a007f674bea16c3a4d9d41739c774b0c063ff79b145d237ca82f58b727b699fd02110000000ed6e19d7c000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 81fd8bd69fdcd4d0acdcae13ea8d7971e3c22d8de854ef4aca3d55337133947d 0.000600000000 1917460 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": 1428747, "vin": [ { "gen": { "height": 1428737 } } ], "vout": [ { "amount": 600000000, "target": { "key": "81fd8bd69fdcd4d0acdcae13ea8d7971e3c22d8de854ef4aca3d55337133947d" } } ], "extra": [ 1, 160, 7, 246, 116, 190, 161, 108, 58, 77, 157, 65, 115, 156, 119, 75, 12, 6, 63, 247, 155, 20, 93, 35, 124, 168, 47, 88, 183, 39, 182, 153, 253, 2, 17, 0, 0, 0, 14, 214, 225, 157, 124, 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: