Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f4634da4f2ad7a89f33e3e6bb6a9c4f620acf9f5b6488f645efadd2a35f6125

Tx prefix hash: 3a8c25bfcd1794c3e787999b35bb8f1d2eadcc2ec5afbf7c1c86633253c7dc84
Tx public key: 8b0092fa0ce5fe04116d676a97947e0bdd0701f6985d500865e6777ad2371593
Timestamp: 1741060399 Timestamp [UTC]: 2025-03-04 03:53:19 Age [y:d:h:m:s]: 01:263:09:30:04
Block: 1231692 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 451802 RingCT/type: yes/0
Extra: 018b0092fa0ce5fe04116d676a97947e0bdd0701f6985d500865e6777ad2371593021100000006007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 84ab4e95495bdfecc3514cfad40bb09b6c5f1be5cc80676952bc3cff5d48a011 0.000600000000 1718603 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": 1231702, "vin": [ { "gen": { "height": 1231692 } } ], "vout": [ { "amount": 600000000, "target": { "key": "84ab4e95495bdfecc3514cfad40bb09b6c5f1be5cc80676952bc3cff5d48a011" } } ], "extra": [ 1, 139, 0, 146, 250, 12, 229, 254, 4, 17, 109, 103, 106, 151, 148, 126, 11, 221, 7, 1, 246, 152, 93, 80, 8, 101, 230, 119, 122, 210, 55, 21, 147, 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: