Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f4fc016edfa89c20646e215de753c1ee397594d2f895bbdab6c8a5628898258

Tx prefix hash: ccd893b011e5368b6547c8158e5c649f8938df7c5459b0c0a01b5222b54b81fe
Tx public key: 7976471ab3e94dbc53a2d380e9bac11ad61891a1623c0ed9fd2226fef2dba29f
Timestamp: 1772021359 Timestamp [UTC]: 2026-02-25 12:09:19 Age [y:d:h:m:s]: 00:080:03:05:08
Block: 1485519 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 49660 RingCT/type: yes/0
Extra: 017976471ab3e94dbc53a2d380e9bac11ad61891a1623c0ed9fd2226fef2dba29f021100000002e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 803ff6d554faff964c68a8a4e10e0cdd4afb671c8e6db41ac3f4b10c124f489b 0.000600000000 1974955 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": 1485529, "vin": [ { "gen": { "height": 1485519 } } ], "vout": [ { "amount": 600000000, "target": { "key": "803ff6d554faff964c68a8a4e10e0cdd4afb671c8e6db41ac3f4b10c124f489b" } } ], "extra": [ 1, 121, 118, 71, 26, 179, 233, 77, 188, 83, 162, 211, 128, 233, 186, 193, 26, 214, 24, 145, 161, 98, 60, 14, 217, 253, 34, 38, 254, 242, 219, 162, 159, 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) | monero version: