Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8122b91c6eca6661e240c78a3d2f9963a2817f9a0d167391c6eef9e9327cfd1e

Tx prefix hash: ed5bd3efaf9621778b92fc8629214f2e0aa4a702be9531380a5c17e2f961beba
Tx public key: 171d9d7ec3a21e587598a20cc580e670db3895602991c9f202fda51ed8a6abe9
Timestamp: 1741329793 Timestamp [UTC]: 2025-03-07 06:43:13 Age [y:d:h:m:s]: 01:171:00:16:54
Block: 1233932 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 386586 RingCT/type: yes/0
Extra: 01171d9d7ec3a21e587598a20cc580e670db3895602991c9f202fda51ed8a6abe90211000000031f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 77c0d0e96e6c406720f29e1ef397553bdf55e3a42729b07d5e6c9ead16d7209e 0.000600000000 1720857 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": 1233942, "vin": [ { "gen": { "height": 1233932 } } ], "vout": [ { "amount": 600000000, "target": { "key": "77c0d0e96e6c406720f29e1ef397553bdf55e3a42729b07d5e6c9ead16d7209e" } } ], "extra": [ 1, 23, 29, 157, 126, 195, 162, 30, 88, 117, 152, 162, 12, 197, 128, 230, 112, 219, 56, 149, 96, 41, 145, 201, 242, 2, 253, 165, 30, 216, 166, 171, 233, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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: