Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5baee2ec9996c3b0211c3bb832bdde1ff6af2c5b1bcbd61569ccb8d0e67dbda1

Tx prefix hash: 56b993ab3bd811bfaab29fd8e92f764a128fe4937680c2bf39c478c9c855e6a7
Tx public key: 9b3e8be08bfa1d267a887ef35d95f1c9c1e8dcfa5b1d1497f95ea8528f30fa24
Timestamp: 1744424512 Timestamp [UTC]: 2025-04-12 02:21:52 Age [y:d:h:m:s]: 01:217:03:39:47
Block: 1259551 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 419135 RingCT/type: yes/0
Extra: 019b3e8be08bfa1d267a887ef35d95f1c9c1e8dcfa5b1d1497f95ea8528f30fa240211000000026c98aa3d000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 316056aa6190bcc44cce782527cfa9a2063d7b724ad5a4db0e4ef6949aa03cad 0.000600000000 1746698 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": 1259561, "vin": [ { "gen": { "height": 1259551 } } ], "vout": [ { "amount": 600000000, "target": { "key": "316056aa6190bcc44cce782527cfa9a2063d7b724ad5a4db0e4ef6949aa03cad" } } ], "extra": [ 1, 155, 62, 139, 224, 139, 250, 29, 38, 122, 136, 126, 243, 93, 149, 241, 201, 193, 232, 220, 250, 91, 29, 20, 151, 249, 94, 168, 82, 143, 48, 250, 36, 2, 17, 0, 0, 0, 2, 108, 152, 170, 61, 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: