Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ddb8acd69b4e191b22f8069676e3b41df2ba32399a7b92b1ddf95b5299bc7118

Tx prefix hash: a34d7f26bd07df0d2c64571c96eba381c27e246f2dc75fbc36e56214f8bf0636
Tx public key: 37e933364edc3850d52ff24a424957812d354033f7b24e593ed51811c74e91d0
Timestamp: 1588736996 Timestamp [UTC]: 2020-05-06 03:49:56 Age [y:d:h:m:s]: 05:307:01:25:07
Block: 99023 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1394125 RingCT/type: yes/0
Extra: 0137e933364edc3850d52ff24a424957812d354033f7b24e593ed51811c74e91d002110000016b37fb5df4000000000000000000

1 output(s) for total of 0.288334399040 xmr

stealth address amount amount idx tag
00: 4d8e261e937521a09b3a9f11c59c1ed2cb1aedb0fa27bc7a9a436d2e86b1c799 0.288334399040 174857 of 0 -

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": 99033, "vin": [ { "gen": { "height": 99023 } } ], "vout": [ { "amount": 288334399040, "target": { "key": "4d8e261e937521a09b3a9f11c59c1ed2cb1aedb0fa27bc7a9a436d2e86b1c799" } } ], "extra": [ 1, 55, 233, 51, 54, 78, 220, 56, 80, 213, 47, 242, 74, 66, 73, 87, 129, 45, 53, 64, 51, 247, 178, 78, 89, 62, 213, 24, 17, 199, 78, 145, 208, 2, 17, 0, 0, 1, 107, 55, 251, 93, 244, 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) | dinastycoin version: tesla-369