Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f642870e3aefd0251f4f72b85f8be3f4777492ad79bf0be38498c853a5df8b45

Tx prefix hash: 607ed1e1d5c571ba4841dfc6647cef5bba8a822135f4a410c189a5867b582653
Tx public key: b44946f1ff423d0750bc3a2e664fc44f010ae183a335843edd735e2902630ded
Timestamp: 1770132833 Timestamp [UTC]: 2026-02-03 15:33:53 Age [y:d:h:m:s]: 00:014:10:24:08
Block: 1469858 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10187 RingCT/type: yes/0
Extra: 01b44946f1ff423d0750bc3a2e664fc44f010ae183a335843edd735e2902630ded021100000002e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: f721809d8c2904685c7ca6f355c881bff4e81e3c1f6ba4405d1ec8eaf7b5ff1c 0.000600000000 1959124 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": 1469868, "vin": [ { "gen": { "height": 1469858 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f721809d8c2904685c7ca6f355c881bff4e81e3c1f6ba4405d1ec8eaf7b5ff1c" } } ], "extra": [ 1, 180, 73, 70, 241, 255, 66, 61, 7, 80, 188, 58, 46, 102, 79, 196, 79, 1, 10, 225, 131, 163, 53, 132, 62, 221, 115, 94, 41, 2, 99, 13, 237, 2, 17, 0, 0, 0, 2, 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) | dinastycoin version: tesla-369