Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c4e101ad1fdf815f41b0cae7968552c0d316711a3a552ea21f033f5f8de993dc

Tx prefix hash: 620e7debf0d6537c15ece045e09f296032416fceb839ef3fa666b443155cc1cf
Tx public key: ef31cc90352d04007d09eb940fc7712c53de543346cb6811527b053e7ac9b8f8
Timestamp: 1576425605 Timestamp [UCT]: 2019-12-15 16:00:05 Age [y:d:h:m:s]: 05:050:00:43:01
Block: 27557 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1182339 RingCT/type: yes/0
Extra: 01ef31cc90352d04007d09eb940fc7712c53de543346cb6811527b053e7ac9b8f80211000000799159db1e000000000000000000

1 output(s) for total of 497.385459954000 dcy

stealth address amount amount idx
00: 8e595cacbab7ab184b6ce8958c73c3d849ca794f237a907aebcb94d5a24bdfe3 497.385459954000 45569 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 dinasty-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": 27567, "vin": [ { "gen": { "height": 27557 } } ], "vout": [ { "amount": 497385459954, "target": { "key": "8e595cacbab7ab184b6ce8958c73c3d849ca794f237a907aebcb94d5a24bdfe3" } } ], "extra": [ 1, 239, 49, 204, 144, 53, 45, 4, 0, 125, 9, 235, 148, 15, 199, 113, 44, 83, 222, 84, 51, 70, 203, 104, 17, 82, 123, 5, 62, 122, 201, 184, 248, 2, 17, 0, 0, 0, 121, 145, 89, 219, 30, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8