Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3258e44c98663579ffec208cb4eb2ff577cf64ade0a58b6d2006156d9c514b55

Tx prefix hash: 46e8c9be8c7c1a29371f11675b96c0daf8484922fb99066c732f30591a26f0dd
Tx public key: 8460e14efb6a001c1e110f43ac6e0b338133810b767464296b76fbea067ae7d0
Timestamp: 1713046256 Timestamp [UTC]: 2024-04-13 22:10:56 Age [y:d:h:m:s]: 01:317:12:06:03
Block: 999887 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 485569 RingCT/type: yes/0
Extra: 018460e14efb6a001c1e110f43ac6e0b338133810b767464296b76fbea067ae7d00211000000030011055b000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a914c4fde6cfa35392471b936f8d0d67af399b24fa44036a1e62d5a14d9f233d 0.000600000000 1460375 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": 999897, "vin": [ { "gen": { "height": 999887 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a914c4fde6cfa35392471b936f8d0d67af399b24fa44036a1e62d5a14d9f233d" } } ], "extra": [ 1, 132, 96, 225, 78, 251, 106, 0, 28, 30, 17, 15, 67, 172, 110, 11, 51, 129, 51, 129, 11, 118, 116, 100, 41, 107, 118, 251, 234, 6, 122, 231, 208, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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