Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64a88f41ea5aea074f00c6a4b366ec42d8a94e9941258721d937b83b3c328ba6

Tx prefix hash: a8570397c4efcc0dcd4e03437cfd59f5ac0ca65e8694f9e686a9419e61190f49
Tx public key: 23bad2523c4d9b1fe9bad4acb72e89e85d5b75f449e380a18b1c93204575194f
Timestamp: 1719614933 Timestamp [UTC]: 2024-06-28 22:48:53 Age [y:d:h:m:s]: 01:323:06:43:44
Block: 1054360 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 482074 RingCT/type: yes/0
Extra: 0123bad2523c4d9b1fe9bad4acb72e89e85d5b75f449e380a18b1c93204575194f0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 81c8b75f8598a149cf8d1f5ea0307454dbc51dc4f271311763ef96b7dd0e86ee 0.000600000000 1524721 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": 1054370, "vin": [ { "gen": { "height": 1054360 } } ], "vout": [ { "amount": 600000000, "target": { "key": "81c8b75f8598a149cf8d1f5ea0307454dbc51dc4f271311763ef96b7dd0e86ee" } } ], "extra": [ 1, 35, 186, 210, 82, 60, 77, 155, 31, 233, 186, 212, 172, 183, 46, 137, 232, 93, 91, 117, 244, 73, 227, 128, 161, 139, 28, 147, 32, 69, 117, 25, 79, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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: