Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 39bb7f73b94b8c04358b1ec36f71bd47e5663a73bc25c93e2834adf6c06c5e3a

Tx prefix hash: 8166d989331af4ba0ed3f89f183aa212c0a6eb68177af708d50f97078bb4028e
Tx public key: 2a4a15fec81c42b099f0903493af9fd3bc3670926ef164f3a4dd083ec489fd0a
Timestamp: 1743511380 Timestamp [UTC]: 2025-04-01 12:43:00 Age [y:d:h:m:s]: 01:144:15:08:47
Block: 1251978 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 367700 RingCT/type: yes/0
Extra: 012a4a15fec81c42b099f0903493af9fd3bc3670926ef164f3a4dd083ec489fd0a021100000006a2ed016b000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a42c92779d501bffc4279a4ac64adc2114470740ed4b9e742f63dca01e80bc0a 0.000600000000 1739055 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": 1251988, "vin": [ { "gen": { "height": 1251978 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a42c92779d501bffc4279a4ac64adc2114470740ed4b9e742f63dca01e80bc0a" } } ], "extra": [ 1, 42, 74, 21, 254, 200, 28, 66, 176, 153, 240, 144, 52, 147, 175, 159, 211, 188, 54, 112, 146, 110, 241, 100, 243, 164, 221, 8, 62, 196, 137, 253, 10, 2, 17, 0, 0, 0, 6, 162, 237, 1, 107, 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: