Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad42c98064180c9d826d39eede8e7ef63a85b3433fbc8d5bb8dcd2e9c7df5f8a

Tx prefix hash: 2e454c8b6207f36f04d7975ce4358611785261cc4a4ff72b32149ca609bf8d6b
Tx public key: bcc3fc74617ef3a886e86f5be011452f8a8208aa9ab9a9610699e7c0d2b49de3
Timestamp: 1747075266 Timestamp [UTC]: 2025-05-12 18:41:06 Age [y:d:h:m:s]: 01:171:09:14:27
Block: 1281486 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 385112 RingCT/type: yes/0
Extra: 01bcc3fc74617ef3a886e86f5be011452f8a8208aa9ab9a9610699e7c0d2b49de30211000000029f9fe68c000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 4c7c894d68c1f08f939b8d2d813721f58963aafd74e0c80058d8ae791d51b4f5 0.000600000000 1768885 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": 1281496, "vin": [ { "gen": { "height": 1281486 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4c7c894d68c1f08f939b8d2d813721f58963aafd74e0c80058d8ae791d51b4f5" } } ], "extra": [ 1, 188, 195, 252, 116, 97, 126, 243, 168, 134, 232, 111, 91, 224, 17, 69, 47, 138, 130, 8, 170, 154, 185, 169, 97, 6, 153, 231, 192, 210, 180, 157, 227, 2, 17, 0, 0, 0, 2, 159, 159, 230, 140, 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: