Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 536dc7d335446db3f87d9e68a018efedec99920bf2a3c28ae5ee55a44f27eb7d

Tx prefix hash: 7b63bad16e8d8f8272418bd086da04bf7765a24ada1fcf32b4e17353c55df5be
Tx public key: a581e20267bff4a22768f652b0f63d14c6dfff16494d8983edc88d83854f3145
Timestamp: 1577175432 Timestamp [UCT]: 2019-12-24 08:17:12 Age [y:d:h:m:s]: 05:047:02:50:46
Block: 30522 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1183519 RingCT/type: yes/0
Extra: 01a581e20267bff4a22768f652b0f63d14c6dfff16494d8983edc88d83854f3145021100000096feadaf7f000000000000000000

1 output(s) for total of 486.260290536000 dcy

stealth address amount amount idx
00: 26d38d01be62312dad63c9cbe5c006928ee6c1fc15cfd45282fe6ccc786f373c 486.260290536000 50398 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": 30532, "vin": [ { "gen": { "height": 30522 } } ], "vout": [ { "amount": 486260290536, "target": { "key": "26d38d01be62312dad63c9cbe5c006928ee6c1fc15cfd45282fe6ccc786f373c" } } ], "extra": [ 1, 165, 129, 226, 2, 103, 191, 244, 162, 39, 104, 246, 82, 176, 246, 61, 20, 198, 223, 255, 22, 73, 77, 137, 131, 237, 200, 141, 131, 133, 79, 49, 69, 2, 17, 0, 0, 0, 150, 254, 173, 175, 127, 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