Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ce102903aab37d1db1fb13b95c6cf3a58b4986628db39467af1bb45fb9e69082

Tx prefix hash: 2b082d2224e8a4f3c23d828a7e26854b8a0eb3ff9bfd771f1e17b5f33c93a983
Tx public key: c13569c77de7ba26335fad781d4c2af5439c976b8ecdb731f207d118903b7a3c
Timestamp: 1583614907 Timestamp [UCT]: 2020-03-07 21:01:47 Age [y:d:h:m:s]: 04:299:01:16:57
Block: 78127 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1108600 RingCT/type: yes/0
Extra: 01c13569c77de7ba26335fad781d4c2af5439c976b8ecdb731f207d118903b7a3c0211000000134ac5aa02000000000000000000

1 output(s) for total of 338.168857022000 dcy

stealth address amount amount idx
00: 2b9fc57efb78b64d12fb0e2b4e3d5fc056ae77233cfd229dcc1435a18ad564bb 338.168857022000 143526 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": 78137, "vin": [ { "gen": { "height": 78127 } } ], "vout": [ { "amount": 338168857022, "target": { "key": "2b9fc57efb78b64d12fb0e2b4e3d5fc056ae77233cfd229dcc1435a18ad564bb" } } ], "extra": [ 1, 193, 53, 105, 199, 125, 231, 186, 38, 51, 95, 173, 120, 29, 76, 42, 245, 67, 156, 151, 107, 142, 205, 183, 49, 242, 7, 209, 24, 144, 59, 122, 60, 2, 17, 0, 0, 0, 19, 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