Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 814731ee66535c411550e7bb5ab1789bf82e3000fa9f9dd408c10fd05bbf00db

Tx prefix hash: 61a4886888e9cf30d6d328a52d87db838fc6d3570482ebda3b0ec89c6a727117
Tx public key: 8a242f3a3d5979a4629fed527033ab81900d423277c37c59b103048c288d37d9
Timestamp: 1769823041 Timestamp [UTC]: 2026-01-31 01:30:41 Age [y:d:h:m:s]: 00:295:12:24:10
Block: 1467282 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 216212 RingCT/type: yes/0
Extra: 018a242f3a3d5979a4629fed527033ab81900d423277c37c59b103048c288d37d902110000000749d73e98000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 2fdf240f8e4268f50cd79116085f775ef4dc5295f2bb87ab4797ccc678d9d19e 0.000600000000 1956522 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": 1467292, "vin": [ { "gen": { "height": 1467282 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2fdf240f8e4268f50cd79116085f775ef4dc5295f2bb87ab4797ccc678d9d19e" } } ], "extra": [ 1, 138, 36, 47, 58, 61, 89, 121, 164, 98, 159, 237, 82, 112, 51, 171, 129, 144, 13, 66, 50, 119, 195, 124, 89, 177, 3, 4, 140, 40, 141, 55, 217, 2, 17, 0, 0, 0, 7, 73, 215, 62, 152, 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: