Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 01ff176747516acb04cc55b3bec2b239b2fa26ca33da66372864818bddfaa007

Tx prefix hash: 85ff4d26393a8d56c3de085540a5eb77c8e6b5ee6db4bb6b88b070159f9bd364
Tx public key: 19c8140bb185b1eb64e9436b06da996b2f4f59e9c9a852a51d9e38b72cce0392
Timestamp: 1771512377 Timestamp [UTC]: 2026-02-19 14:46:17 Age [y:d:h:m:s]: 00:270:21:42:05
Block: 1481266 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 199106 RingCT/type: yes/0
Extra: 0119c8140bb185b1eb64e9436b06da996b2f4f59e9c9a852a51d9e38b72cce0392021100000003e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 67e466dc69a77f4d0b06123c0b5787134402094f1c3a9c55845dc1586f29cc57 0.000600000000 1970642 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": 1481276, "vin": [ { "gen": { "height": 1481266 } } ], "vout": [ { "amount": 600000000, "target": { "key": "67e466dc69a77f4d0b06123c0b5787134402094f1c3a9c55845dc1586f29cc57" } } ], "extra": [ 1, 25, 200, 20, 11, 177, 133, 177, 235, 100, 233, 67, 107, 6, 218, 153, 107, 47, 79, 89, 233, 201, 168, 82, 165, 29, 158, 56, 183, 44, 206, 3, 146, 2, 17, 0, 0, 0, 3, 228, 245, 25, 63, 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: