Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b77c35b5973f8fc6cb60194931f0104f3e47dfe09c985d45c17520db75abb22a

Tx prefix hash: 687ba29ada35b17eb1c55b04cef812d8206b113e64c9590f4e4a1b96b5238334
Tx public key: b1a3d9790d6610ad9f9e44e85b88cff733ed4805ee8c39569ae26bdac28c2073
Timestamp: 1774066126 Timestamp [UTC]: 2026-03-21 04:08:46 Age [y:d:h:m:s]: 00:245:22:55:58
Block: 1502379 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181115 RingCT/type: yes/0
Extra: 01b1a3d9790d6610ad9f9e44e85b88cff733ed4805ee8c39569ae26bdac28c2073021100000002f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 70903a755121e831e04b86789378b9d6594456ed6694f5da6d8f078167d8bff5 0.000600000000 1992077 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": 1502389, "vin": [ { "gen": { "height": 1502379 } } ], "vout": [ { "amount": 600000000, "target": { "key": "70903a755121e831e04b86789378b9d6594456ed6694f5da6d8f078167d8bff5" } } ], "extra": [ 1, 177, 163, 217, 121, 13, 102, 16, 173, 159, 158, 68, 232, 91, 136, 207, 247, 51, 237, 72, 5, 238, 140, 57, 86, 154, 226, 107, 218, 194, 140, 32, 115, 2, 17, 0, 0, 0, 2, 241, 136, 200, 168, 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: