Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 837cf6c2d288498a589ca11a1ebac4e29ebf46f34dd56793d1ea0e0c6a3aa72d

Tx prefix hash: 4748e9875e6471a560c59e07ec745b03708efdbd4ac93ade0e40becb3a1c9a07
Tx public key: 844b2f8eba4c6ac5d1884d26f00faf3635b67a8c43248c495b7b7fccca0fe0ae
Timestamp: 1577449207 Timestamp [UCT]: 2019-12-27 12:20:07 Age [y:d:h:m:s]: 05:310:06:44:48
Block: 32864 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1369264 RingCT/type: yes/0
Extra: 01844b2f8eba4c6ac5d1884d26f00faf3635b67a8c43248c495b7b7fccca0fe0ae0211000001c9e39b962a000000000000000000

1 output(s) for total of 477.648901834000 dcy

stealth address amount amount idx
00: 58be94563b5a9bf62de95e07af9c0c1f5b3245fea704e89e4c735be2ab9a14c7 477.648901834000 54753 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": 32874, "vin": [ { "gen": { "height": 32864 } } ], "vout": [ { "amount": 477648901834, "target": { "key": "58be94563b5a9bf62de95e07af9c0c1f5b3245fea704e89e4c735be2ab9a14c7" } } ], "extra": [ 1, 132, 75, 47, 142, 186, 76, 106, 197, 209, 136, 77, 38, 240, 15, 175, 54, 53, 182, 122, 140, 67, 36, 140, 73, 91, 123, 127, 204, 202, 15, 224, 174, 2, 17, 0, 0, 1, 201, 227, 155, 150, 42, 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