Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5cff770eba653bb0140f1f7fda779328a7b793aa8822e06b111b791265ff01f8

Tx prefix hash: 868e6fa841c9008a469251183363000329e2c2cdfc4fc009f4b2324b05703f56
Tx public key: e1fac0e6c99784604084bde181e8841f40d37f622137d32c6409687379b760f2
Timestamp: 1773473231 Timestamp [UTC]: 2026-03-14 07:27:11 Age [y:d:h:m:s]: 00:246:04:26:32
Block: 1497486 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181387 RingCT/type: yes/0
Extra: 01e1fac0e6c99784604084bde181e8841f40d37f622137d32c6409687379b760f2021100000003e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 2a3ec0ca56f05aea39f1a3a015967a7f08bb82afc9780a9f41d9609061052a6f 0.000600000000 1987124 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": 1497496, "vin": [ { "gen": { "height": 1497486 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2a3ec0ca56f05aea39f1a3a015967a7f08bb82afc9780a9f41d9609061052a6f" } } ], "extra": [ 1, 225, 250, 192, 230, 201, 151, 132, 96, 64, 132, 189, 225, 129, 232, 132, 31, 64, 211, 127, 98, 33, 55, 211, 44, 100, 9, 104, 115, 121, 183, 96, 242, 2, 17, 0, 0, 0, 3, 228, 245, 25, 63, 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: