Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5a16f993842a9d16e40b0a26330ee899b41bea6c896eafd9d8d3f19e12cd0e1

Tx prefix hash: 7dcbe3c57016ec78baf10f6f2d85a0e11d7ec5de5d82c56266eb452134f5345c
Tx public key: 7eae6be41b9c827bab47a741e22832541a1f4d3caf48e8ed558e00c0b370f379
Timestamp: 1724737060 Timestamp [UTC]: 2024-08-27 05:37:40 Age [y:d:h:m:s]: 02:080:23:11:50
Block: 1096812 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 582596 RingCT/type: yes/0
Extra: 017eae6be41b9c827bab47a741e22832541a1f4d3caf48e8ed558e00c0b370f379021100000008e914dd15000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: aea5fcd6853a4a346049452cf6e3263269ca9643e4b05063cd911fe2b3d9f35e 0.000600000000 1572007 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": 1096822, "vin": [ { "gen": { "height": 1096812 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aea5fcd6853a4a346049452cf6e3263269ca9643e4b05063cd911fe2b3d9f35e" } } ], "extra": [ 1, 126, 174, 107, 228, 27, 156, 130, 123, 171, 71, 167, 65, 226, 40, 50, 84, 26, 31, 77, 60, 175, 72, 232, 237, 85, 142, 0, 192, 179, 112, 243, 121, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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: