Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 53e274b50f4856f9f928add0a8d9ec24112f72cdec364d5c702013bbd94739dc

Tx prefix hash: 40fe5ae2827ac74ac98ecad401f535a14800a5447f56f9d13d98ce0aa9b42198
Tx public key: e7c87e92e3da401f6bed5f045b4ad334b8e2b75e1460098daad32cb85f4ac2b5
Timestamp: 1577938421 Timestamp [UCT]: 2020-01-02 04:13:41 Age [y:d:h:m:s]: 05:049:00:13:43
Block: 36903 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1184766 RingCT/type: yes/0
Extra: 01e7c87e92e3da401f6bed5f045b4ad334b8e2b75e1460098daad32cb85f4ac2b502110000002b4ac5aa02000000000000000000

1 output(s) for total of 463.154506401000 dcy

stealth address amount amount idx
00: d01d647a1fa266fa9f41b5c2c4d0af09a5b201356c52e5a2f5b690337e4eabd2 463.154506401000 62569 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": 36913, "vin": [ { "gen": { "height": 36903 } } ], "vout": [ { "amount": 463154506401, "target": { "key": "d01d647a1fa266fa9f41b5c2c4d0af09a5b201356c52e5a2f5b690337e4eabd2" } } ], "extra": [ 1, 231, 200, 126, 146, 227, 218, 64, 31, 107, 237, 95, 4, 91, 74, 211, 52, 184, 226, 183, 94, 20, 96, 9, 141, 170, 211, 44, 184, 95, 74, 194, 181, 2, 17, 0, 0, 0, 43, 74, 197, 170, 2, 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