Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d72ee5d6ac73309754d34138e8f7f9ffedf122eb8f32da36ce70b42d67fb623

Tx prefix hash: fff96c8b212262a1b4f4a8c9085b1f5e242717e3d00265be6a585b3184d3aab1
Tx public key: 289a75b6470cdbb8f85299836c7966513d174a277ebc554ba9ffaa27a63ba8c6
Timestamp: 1641637109 Timestamp [UTC]: 2022-01-08 10:18:29 Age [y:d:h:m:s]: 04:129:23:31:27
Block: 412939 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1122845 RingCT/type: yes/0
Extra: 01289a75b6470cdbb8f85299836c7966513d174a277ebc554ba9ffaa27a63ba8c602110000008aed5d3ead000000000000000000

1 output(s) for total of 0.026288869981 xmr

stealth address amount amount idx tag
00: c58a3e7ed0b33ced800a64177e905a048bfcb5e9ce0ac2dbf5b36f3ae3353902 0.026288869981 817332 of 0 -

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": 412949, "vin": [ { "gen": { "height": 412939 } } ], "vout": [ { "amount": 26288869981, "target": { "key": "c58a3e7ed0b33ced800a64177e905a048bfcb5e9ce0ac2dbf5b36f3ae3353902" } } ], "extra": [ 1, 40, 154, 117, 182, 71, 12, 219, 184, 248, 82, 153, 131, 108, 121, 102, 81, 61, 23, 74, 39, 126, 188, 85, 75, 169, 255, 170, 39, 166, 59, 168, 198, 2, 17, 0, 0, 0, 138, 237, 93, 62, 173, 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: