Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6118fea3ada8ccb43947f26787c8981e48a8120b41fec59ec6fc95bc7e1b969d

Tx prefix hash: 1bd27040a473831577ce750e7d1818be8dce2e95e7d0c1a57cfa25492487fc25
Tx public key: 090fd6bb78c39303de8b2f385514c900280319f38297a53b295a3fc6bbbabf18
Timestamp: 1674412033 Timestamp [UTC]: 2023-01-22 18:27:13 Age [y:d:h:m:s]: 03:303:08:56:10
Block: 680487 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1002644 RingCT/type: yes/0
Extra: 01090fd6bb78c39303de8b2f385514c900280319f38297a53b295a3fc6bbbabf18021100000001272bcc39000000000000000000

1 output(s) for total of 0.003414004013 xmr

stealth address amount amount idx tag
00: e83584413bbc2175b6d5a6a06797889e2048c2c396bd38512e928e193c3845f1 0.003414004013 1122536 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": 680497, "vin": [ { "gen": { "height": 680487 } } ], "vout": [ { "amount": 3414004013, "target": { "key": "e83584413bbc2175b6d5a6a06797889e2048c2c396bd38512e928e193c3845f1" } } ], "extra": [ 1, 9, 15, 214, 187, 120, 195, 147, 3, 222, 139, 47, 56, 85, 20, 201, 0, 40, 3, 25, 243, 130, 151, 165, 59, 41, 90, 63, 198, 187, 186, 191, 24, 2, 17, 0, 0, 0, 1, 39, 43, 204, 57, 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: