Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5bbbea046f5984e3571bc17a56061a8d7323a28d233cf4af0f454acc7e150a7d

Tx prefix hash: a840f5e3d7dd41d199843c4be9c809f1b4fa1904b05740908aad826c38b805a2
Tx public key: 9558634aace8ae41dbf4761193959aadac1218f8fa17f5638aa17d8054fbb391
Timestamp: 1772810223 Timestamp [UTC]: 2026-03-06 15:17:03 Age [y:d:h:m:s]: 00:072:18:29:23
Block: 1492017 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 44560 RingCT/type: yes/0
Extra: 019558634aace8ae41dbf4761193959aadac1218f8fa17f5638aa17d8054fbb391021100000004f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: d8df00d4259f6a1c01a992f5d835246744b6efcf34475f3fbd4365d6254a2b64 0.000600000000 1981555 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": 1492027, "vin": [ { "gen": { "height": 1492017 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d8df00d4259f6a1c01a992f5d835246744b6efcf34475f3fbd4365d6254a2b64" } } ], "extra": [ 1, 149, 88, 99, 74, 172, 232, 174, 65, 219, 244, 118, 17, 147, 149, 154, 173, 172, 18, 24, 248, 250, 23, 245, 99, 138, 161, 125, 128, 84, 251, 179, 145, 2, 17, 0, 0, 0, 4, 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: