Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 28e5690cd97beafea50067e4ce98d86a9827996ca7f18805ea04550dc1c686f9

Tx prefix hash: 5a289686a1904c70ae006a8686dbcbba56d283b33ff8b6a3757881b215ffadcd
Tx public key: 3e5c363938419747a5218ac5611f5f9fd5b1008296bc0bffdc0e69c10498690d
Timestamp: 1721996695 Timestamp [UTC]: 2024-07-26 12:24:55 Age [y:d:h:m:s]: 02:118:03:24:47
Block: 1074104 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 609390 RingCT/type: yes/0
Extra: 013e5c363938419747a5218ac5611f5f9fd5b1008296bc0bffdc0e69c10498690d02110000000191e13c04000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 424abeb6bb6877ce99c975fd2d98863df1ca346635a3f3192530a4a2209524dc 0.000600000000 1546617 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": 1074114, "vin": [ { "gen": { "height": 1074104 } } ], "vout": [ { "amount": 600000000, "target": { "key": "424abeb6bb6877ce99c975fd2d98863df1ca346635a3f3192530a4a2209524dc" } } ], "extra": [ 1, 62, 92, 54, 57, 56, 65, 151, 71, 165, 33, 138, 197, 97, 31, 95, 159, 213, 177, 0, 130, 150, 188, 11, 255, 220, 14, 105, 193, 4, 152, 105, 13, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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: