Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a3a5dbff593aa41dece67d87ea9eab437951d8789dce9129c19560a2c67530ea

Tx prefix hash: b0545b96dfcf601da70f890804cb71b67d6a176ca25c689c2ea60044762436d2
Tx public key: 42ca671dc99f0f789cdd7e33852b1aa313878af13ae417b66c02ef2eec98423e
Timestamp: 1617645604 Timestamp [UTC]: 2021-04-05 18:00:04 Age [y:d:h:m:s]: 05:226:03:44:00
Block: 233868 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1446061 RingCT/type: yes/0
Extra: 0142ca671dc99f0f789cdd7e33852b1aa313878af13ae417b66c02ef2eec98423e0211000000123a645b90000000000000000000

1 output(s) for total of 0.103062057588 xmr

stealth address amount amount idx tag
00: f880ea0b0e1af308abeff7a57b679d4d95a16b041aa9449c9a505b0f3e6e328b 0.103062057588 485556 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": 233878, "vin": [ { "gen": { "height": 233868 } } ], "vout": [ { "amount": 103062057588, "target": { "key": "f880ea0b0e1af308abeff7a57b679d4d95a16b041aa9449c9a505b0f3e6e328b" } } ], "extra": [ 1, 66, 202, 103, 29, 201, 159, 15, 120, 156, 221, 126, 51, 133, 43, 26, 163, 19, 135, 138, 241, 58, 228, 23, 182, 108, 2, 239, 46, 236, 152, 66, 62, 2, 17, 0, 0, 0, 18, 58, 100, 91, 144, 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: