Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 697d344b39d2995c0612b50e741a68d4af39aa74b7299f57c76a6a5dc6f82cdb

Tx prefix hash: 7769fdc011e9be97c5c2114035c5488d44e1ddc1f451f4d6a28eebbbb5c21c47
Tx public key: 7a31dea85bc6c9e91c1eee9b547dd443b4c325bf862af578a8487890de92eed3
Timestamp: 1744259698 Timestamp [UTC]: 2025-04-10 04:34:58 Age [y:d:h:m:s]: 01:164:00:59:02
Block: 1258178 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 381973 RingCT/type: yes/0
Extra: 017a31dea85bc6c9e91c1eee9b547dd443b4c325bf862af578a8487890de92eed302110000000d6c98aa3d000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 9ee50346bf5517f4c5bac1b828e640da58d597da541f886bec3da27290343cf6 0.000600000000 1745311 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": 1258188, "vin": [ { "gen": { "height": 1258178 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9ee50346bf5517f4c5bac1b828e640da58d597da541f886bec3da27290343cf6" } } ], "extra": [ 1, 122, 49, 222, 168, 91, 198, 201, 233, 28, 30, 238, 155, 84, 125, 212, 67, 180, 195, 37, 191, 134, 42, 245, 120, 168, 72, 120, 144, 222, 146, 238, 211, 2, 17, 0, 0, 0, 13, 108, 152, 170, 61, 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: