Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a3a6be99a90e2d936a407dcfaf177993cfda4501627cc1259e4e754d2b8537b8

Tx prefix hash: 05807afc1e4aba98e169ebbf1690fa22a3102944d93b8858f6bf1c9ba77f62ec
Tx public key: e7a0e6e5fd78f58e1f6e72d86cac0c1dd27d4aa78b04d500c08a345d6a30fa5e
Timestamp: 1788906416 Timestamp [UTC]: 2026-09-08 22:26:56 Age [y:d:h:m:s]: 00:066:12:30:22
Block: 1631202 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 46891 RingCT/type: yes/0
Extra: 01e7a0e6e5fd78f58e1f6e72d86cac0c1dd27d4aa78b04d500c08a345d6a30fa5e

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: cf4dfe9c98ef51a081dfdf56a55869fa4212e0133b5fcec9f64e8e3edc3aa7ea 0.000600000000 2121222 of 15 <b0>

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": 1631212, "vin": [ { "gen": { "height": 1631202 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "cf4dfe9c98ef51a081dfdf56a55869fa4212e0133b5fcec9f64e8e3edc3aa7ea", "view_tag": "b0" } } } ], "extra": [ 1, 231, 160, 230, 229, 253, 120, 245, 142, 31, 110, 114, 216, 108, 172, 12, 29, 210, 125, 74, 167, 139, 4, 213, 0, 192, 138, 52, 93, 106, 48, 250, 94 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: