Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db0e3a641becab67587988c27643fb25180865e7b4d765fbe367d17ae393eae9

Tx prefix hash: 8592b50157d64942abfd931c4f42127d916d55761c2778b374da5fc3d1bf4e9f
Tx public key: c68610daa4ca055d1c803d39456a87fe2544ed3ec69f94117e3abb0576c9c043
Timestamp: 1744036690 Timestamp [UTC]: 2025-04-07 14:38:10 Age [y:d:h:m:s]: 01:032:18:48:50
Block: 1256331 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 274661 RingCT/type: yes/0
Extra: 01c68610daa4ca055d1c803d39456a87fe2544ed3ec69f94117e3abb0576c9c04302110000000cdbb571c1000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 5ee7eab2950d3a46fa60a63d9a0ee8c0d40038a61e2a4fa12c84c35bee1e18a4 0.000600000000 1743444 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": 1256341, "vin": [ { "gen": { "height": 1256331 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5ee7eab2950d3a46fa60a63d9a0ee8c0d40038a61e2a4fa12c84c35bee1e18a4" } } ], "extra": [ 1, 198, 134, 16, 218, 164, 202, 5, 93, 28, 128, 61, 57, 69, 106, 135, 254, 37, 68, 237, 62, 198, 159, 148, 17, 126, 58, 187, 5, 118, 201, 192, 67, 2, 17, 0, 0, 0, 12, 219, 181, 113, 193, 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: