Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 27369abf4ddae5c1db283d387389c0e7158d76a4cfcf230086560d6603328ea2

Tx prefix hash: 629c055ac3a4b00298b633cae8fa9ade0026aba25472c80de6a9de327aa3c04f
Tx public key: dd2317c1a72247bbb2f29eaef107c638989e790293d4ba65172cd903a56069b1
Timestamp: 1607866903 Timestamp [UTC]: 2020-12-13 13:41:43 Age [y:d:h:m:s]: 05:345:07:57:19
Block: 161233 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1522917 RingCT/type: yes/0
Extra: 01dd2317c1a72247bbb2f29eaef107c638989e790293d4ba65172cd903a56069b102110000046fc6b81c9d000000000000000000

1 output(s) for total of 0.179385181783 xmr

stealth address amount amount idx tag
00: ee1321b74006d5eab8f4b3fb3eb291c5cd705d9697b5c7bcd4db7f92349ad480 0.179385181783 285384 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": 161243, "vin": [ { "gen": { "height": 161233 } } ], "vout": [ { "amount": 179385181783, "target": { "key": "ee1321b74006d5eab8f4b3fb3eb291c5cd705d9697b5c7bcd4db7f92349ad480" } } ], "extra": [ 1, 221, 35, 23, 193, 167, 34, 71, 187, 178, 242, 158, 174, 241, 7, 198, 56, 152, 158, 121, 2, 147, 212, 186, 101, 23, 44, 217, 3, 165, 96, 105, 177, 2, 17, 0, 0, 4, 111, 198, 184, 28, 157, 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: