Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb9c75faf6c39862c1b91be57edabaeefc6479c1cd14a19829444cdece4c2e2d

Tx prefix hash: 428f33aa34773a8377bf11c709235901d2da3d54694fb26af294f748a32f9043
Tx public key: 67c0fed87b891b2b49983310c0f61e29b0bc62d020b192e1db368b00ec6f2336
Timestamp: 1774180855 Timestamp [UTC]: 2026-03-22 12:00:55 Age [y:d:h:m:s]: 00:238:17:59:29
Block: 1503329 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176114 RingCT/type: yes/0
Extra: 0167c0fed87b891b2b49983310c0f61e29b0bc62d020b192e1db368b00ec6f2336021100000007f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 233505ba45a6451f9e195a23a8923f53d83621ccf267703f61ba784dad7ea5c2 0.000600000000 1993037 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": 1503339, "vin": [ { "gen": { "height": 1503329 } } ], "vout": [ { "amount": 600000000, "target": { "key": "233505ba45a6451f9e195a23a8923f53d83621ccf267703f61ba784dad7ea5c2" } } ], "extra": [ 1, 103, 192, 254, 216, 123, 137, 27, 43, 73, 152, 51, 16, 192, 246, 30, 41, 176, 188, 98, 208, 32, 177, 146, 225, 219, 54, 139, 0, 236, 111, 35, 54, 2, 17, 0, 0, 0, 7, 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: