Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b84f7a3a19c0f7d369a9f804d6e8bfb7f3df07441e608139cc07de2dfbdc6dca

Tx prefix hash: 8f68e8dac6dc44c305060ee2134080c2abfbd631cc83fbea1e87e4e9e4e1a4ca
Tx public key: d2d4159b1ae792ee9b82fc08d4fe7d2fe4df6f0097b18fca845472dfd25f7792
Timestamp: 1734063407 Timestamp [UTC]: 2024-12-13 04:16:47 Age [y:d:h:m:s]: 01:335:11:32:56
Block: 1174058 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 503443 RingCT/type: yes/0
Extra: 01d2d4159b1ae792ee9b82fc08d4fe7d2fe4df6f0097b18fca845472dfd25f7792021100000006007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 4054696ab6ff114344d68508955521e7d75b8147fd0391adaaab95ed3ca6de6f 0.000600000000 1660161 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": 1174068, "vin": [ { "gen": { "height": 1174058 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4054696ab6ff114344d68508955521e7d75b8147fd0391adaaab95ed3ca6de6f" } } ], "extra": [ 1, 210, 212, 21, 155, 26, 231, 146, 238, 155, 130, 252, 8, 212, 254, 125, 47, 228, 223, 111, 0, 151, 177, 143, 202, 132, 84, 114, 223, 210, 95, 119, 146, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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: