Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a079a94ab7a417c602214a01f0a9c1acc0d136bb2315fb9e09fd2e57a5d0f74e

Tx prefix hash: ab605a3b590119f926a716303516e4e0166f238fb13285d190b473a091d31895
Tx public key: 5847e520eb90b770d0a206d7a8f578e24fd635c779b6a8ce8b0bbe093c76f9b6
Timestamp: 1739265151 Timestamp [UTC]: 2025-02-11 09:12:31 Age [y:d:h:m:s]: 01:283:21:31:52
Block: 1216834 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 466660 RingCT/type: yes/0
Extra: 015847e520eb90b770d0a206d7a8f578e24fd635c779b6a8ce8b0bbe093c76f9b6021100000006007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 2b54dad75d38a2852d007211395ba8eb5f2cc6deaa08796e1dec64c39851cf94 0.000600000000 1703641 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": 1216844, "vin": [ { "gen": { "height": 1216834 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2b54dad75d38a2852d007211395ba8eb5f2cc6deaa08796e1dec64c39851cf94" } } ], "extra": [ 1, 88, 71, 229, 32, 235, 144, 183, 112, 208, 162, 6, 215, 168, 245, 120, 226, 79, 214, 53, 199, 121, 182, 168, 206, 139, 11, 190, 9, 60, 118, 249, 182, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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: