Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a67a7e4904f2825f19e7c8c07f0d5f7c52b1ff5c906d05f4a095e049277ae8cb

Tx prefix hash: f2290ea8e274a97140bb7431854c9fc5aa345fec2f810e43ab02493042a486fd
Tx public key: 2397c47ca68d7effa0bde06d57fc5b8624dc1aa03bec3060955bfcd41eb5de4e
Timestamp: 1577193157 Timestamp [UTC]: 2019-12-24 13:12:37 Age [y:d:h:m:s]: 06:331:18:39:02
Block: 30724 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1651014 RingCT/type: yes/0
Extra: 012397c47ca68d7effa0bde06d57fc5b8624dc1aa03bec3060955bfcd41eb5de4e0211000000d778873133000000000000000000

1 output(s) for total of 0.485511470782 xmr

stealth address amount amount idx tag
00: 1e8b950fc3a49b901cff268800dc614c3f15d5c9bd6dc39ead01af3c0fba00f4 0.485511470782 50724 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": 30734, "vin": [ { "gen": { "height": 30724 } } ], "vout": [ { "amount": 485511470782, "target": { "key": "1e8b950fc3a49b901cff268800dc614c3f15d5c9bd6dc39ead01af3c0fba00f4" } } ], "extra": [ 1, 35, 151, 196, 124, 166, 141, 126, 255, 160, 189, 224, 109, 87, 252, 91, 134, 36, 220, 26, 160, 59, 236, 48, 96, 149, 91, 252, 212, 30, 181, 222, 78, 2, 17, 0, 0, 0, 215, 120, 135, 49, 51, 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: