Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b45a74c7ec2637f2396bf197186dd7bfb7058d7f8b3c7852e1d71bf67df71df6

Tx prefix hash: e1afeb9abe68845583442b21cb645dd36883793ecca1fd7099af5cfa58545b41
Tx public key: c9d48caba63bffbd3170868dd0efe250082e806773112db243c5817cfb238e0d
Timestamp: 1580774525 Timestamp [UCT]: 2020-02-04 00:02:05 Age [y:d:h:m:s]: 05:036:14:28:18
Block: 57953 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1178365 RingCT/type: yes/0
Extra: 01c9d48caba63bffbd3170868dd0efe250082e806773112db243c5817cfb238e0d02112b37a79f00000000000000000000000000

1 output(s) for total of 394.444561921000 dcy

stealth address amount amount idx
00: 5d4c63b02a42ddd8dd84673faef7e0a69a96d21d7bca361eb2d5b2e9d5cc9bd8 394.444561921000 107186 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": 57963, "vin": [ { "gen": { "height": 57953 } } ], "vout": [ { "amount": 394444561921, "target": { "key": "5d4c63b02a42ddd8dd84673faef7e0a69a96d21d7bca361eb2d5b2e9d5cc9bd8" } } ], "extra": [ 1, 201, 212, 140, 171, 166, 59, 255, 189, 49, 112, 134, 141, 208, 239, 226, 80, 8, 46, 128, 103, 115, 17, 45, 178, 67, 197, 129, 124, 251, 35, 142, 13, 2, 17, 43, 55, 167, 159, 0, 0, 0, 0, 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