Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c5e251426a0f8a3d4a4b3aef8a1f0f39933c82e855f11ce32dad844a2dd129bb

Tx prefix hash: 1a47a6d8aeaf24769dc837d08329b95c25749f836db571e4fd9eb39e71d0c512
Tx public key: 0b270d465ae16e05d8b5901211c6c5833744fb393608085c096417407dd882f0
Timestamp: 1767157161 Timestamp [UTC]: 2025-12-31 04:59:21 Age [y:d:h:m:s]: 00:047:19:35:40
Block: 1445371 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 34042 RingCT/type: yes/0
Extra: 010b270d465ae16e05d8b5901211c6c5833744fb393608085c096417407dd882f002110000000149d73e98000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 4bd39d363e7e24f53c0389630118f81d55520d7c70deb4c2a110ec683a338c66 0.000600000000 1934313 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": 1445381, "vin": [ { "gen": { "height": 1445371 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4bd39d363e7e24f53c0389630118f81d55520d7c70deb4c2a110ec683a338c66" } } ], "extra": [ 1, 11, 39, 13, 70, 90, 225, 110, 5, 216, 181, 144, 18, 17, 198, 197, 131, 55, 68, 251, 57, 54, 8, 8, 92, 9, 100, 23, 64, 125, 216, 130, 240, 2, 17, 0, 0, 0, 1, 73, 215, 62, 152, 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) | dinastycoin version: tesla-369