Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 50038802b7ac43a7791842ea17e6e2fd5fe2cabf36f94eea8232612bbae35183

Tx prefix hash: 80ecf378069edcd0e47fa75f5eb219c9d8ccdcc7a1a01fe238e567e81b3e2af1
Tx public key: 7b8fc378b2f4f12e6c12a46b80031b282833c4755e81733eadcff8723dda0dfd
Timestamp: 1588265144 Timestamp [UTC]: 2020-04-30 16:45:44 Age [y:d:h:m:s]: 06:019:20:40:15
Block: 97054 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1441229 RingCT/type: yes/0
Extra: 017b8fc378b2f4f12e6c12a46b80031b282833c4755e81733eadcff8723dda0dfd0211000006fb6fa03929000000000000000000

1 output(s) for total of 0.292698552833 xmr

stealth address amount amount idx tag
00: 4833a457567d9a435c2af64df140eb2519f62fba5f51d95d9c406cc71ce596bd 0.292698552833 172055 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": 97064, "vin": [ { "gen": { "height": 97054 } } ], "vout": [ { "amount": 292698552833, "target": { "key": "4833a457567d9a435c2af64df140eb2519f62fba5f51d95d9c406cc71ce596bd" } } ], "extra": [ 1, 123, 143, 195, 120, 178, 244, 241, 46, 108, 18, 164, 107, 128, 3, 27, 40, 40, 51, 196, 117, 94, 129, 115, 62, 173, 207, 248, 114, 61, 218, 13, 253, 2, 17, 0, 0, 6, 251, 111, 160, 57, 41, 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: