Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d5c9563056fdbf371cfd490ae05d4109092185e43f642efa5f6d86d4f7cc9f6d

Tx prefix hash: 4578b2d6ddd3944e41e888639ce16e41b1d85471eae3286235e1ef427cd01ca5
Tx public key: 35c210483a694cb20f7225373b97094516cb3fb8ea0c879c5a9edb81e51d90e4
Timestamp: 1575332050 Timestamp [UTC]: 2019-12-03 00:14:10 Age [y:d:h:m:s]: 06:091:20:01:51
Block: 21095 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1468196 RingCT/type: yes/0
Extra: 0135c210483a694cb20f7225373b97094516cb3fb8ea0c879c5a9edb81e51d90e4021100000002c4ba021c000000000000000000

1 output(s) for total of 0.522521762730 xmr

stealth address amount amount idx tag
00: a3377b067878e4e4e59100e30c4fee18e9f6d8c3fbf3f7af398cf31a76829eb1 0.522521762730 33656 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": 21105, "vin": [ { "gen": { "height": 21095 } } ], "vout": [ { "amount": 522521762730, "target": { "key": "a3377b067878e4e4e59100e30c4fee18e9f6d8c3fbf3f7af398cf31a76829eb1" } } ], "extra": [ 1, 53, 194, 16, 72, 58, 105, 76, 178, 15, 114, 37, 55, 59, 151, 9, 69, 22, 203, 63, 184, 234, 12, 135, 156, 90, 158, 219, 129, 229, 29, 144, 228, 2, 17, 0, 0, 0, 2, 196, 186, 2, 28, 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