Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 949f1b5d56983f11223f62ef97ac144925f1993f00eb70ef750d01f08c23da55

Tx prefix hash: 20b96d2afeede8e4e9fd2d848e2edb7cce7bc110bc660efe990567e0ce248961
Tx public key: 4b3887c181ceb6cea7c5370217ceb8fdef253224c5591967d800b9eb0f46f226
Timestamp: 1770418033 Timestamp [UTC]: 2026-02-06 22:47:13 Age [y:d:h:m:s]: 00:007:08:52:48
Block: 1472239 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0908 kB
Tx version: 2 No of confirmations: 5236 RingCT/type: yes/0
Extra: 014b3887c181ceb6cea7c5370217ceb8fdef253224c5591967d800b9eb0f46f2260208dc3532e62590042c

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 67e045b45d5e2316e806e6f6d7af165f4ac055bae027ea51d923b87a8c19e51b 0.000600000000 1961517 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": 1472249, "vin": [ { "gen": { "height": 1472239 } } ], "vout": [ { "amount": 600000000, "target": { "key": "67e045b45d5e2316e806e6f6d7af165f4ac055bae027ea51d923b87a8c19e51b" } } ], "extra": [ 1, 75, 56, 135, 193, 129, 206, 182, 206, 167, 197, 55, 2, 23, 206, 184, 253, 239, 37, 50, 36, 197, 89, 25, 103, 216, 0, 185, 235, 15, 70, 242, 38, 2, 8, 220, 53, 50, 230, 37, 144, 4, 44 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | dinastycoin version: tesla-369