Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f7143a4180fee4b013c0eadd7f307f48cda5fa395e6f1116c433d8f6373b0731

Tx prefix hash: 54892373ab672ed05ac670a9bbfdd77dd8b0c20ff8e9faf5ee96886ff06b064e
Tx public key: cf8e3a1bf49ff98dd23fbd2ee9dd337dc4290defce804fb1f605dd0ba7a23792
Timestamp: 1736768253 Timestamp [UTC]: 2025-01-13 11:37:33 Age [y:d:h:m:s]: 01:116:14:48:04
Block: 1196428 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 334349 RingCT/type: yes/0
Extra: 01cf8e3a1bf49ff98dd23fbd2ee9dd337dc4290defce804fb1f605dd0ba7a23792021100000001007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 2a41910279f109f88758913478bf014d0fbadbc44f9baa7c05b7757d56a89f2c 0.000600000000 1683027 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": 1196438, "vin": [ { "gen": { "height": 1196428 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2a41910279f109f88758913478bf014d0fbadbc44f9baa7c05b7757d56a89f2c" } } ], "extra": [ 1, 207, 142, 58, 27, 244, 159, 249, 141, 210, 63, 189, 46, 233, 221, 51, 125, 196, 41, 13, 239, 206, 128, 79, 177, 246, 5, 221, 11, 167, 162, 55, 146, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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: