Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 678aad8fbeb3842a41f574a842815639e3da1effa9642e90bc1226d808029179

Tx prefix hash: 9aadad4a9948e0541475bff4583159a4849ad4eb951a3e4cb7f7d6ff7f751dde
Tx public key: f1e58baa23d38118d2b77d3af205e1a1be95f41090be2e4f5a444d4728138bf5
Timestamp: 1629704445 Timestamp [UCT]: 2021-08-23 07:40:45 Age [y:d:h:m:s]: 04:074:00:28:22
Block: 319156 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1085506 RingCT/type: yes/0
Extra: 01f1e58baa23d38118d2b77d3af205e1a1be95f41090be2e4f5a444d4728138bf502110000000f17696b73000000000000000000

1 output(s) for total of 53.767076642000 dcy

stealth address amount amount idx
00: 0aaaa91b1bd9920a70ddb63a52c4b6da80d9ecfa5edc6751d020a8c9b97f36b8 53.767076642000 663161 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": 319166, "vin": [ { "gen": { "height": 319156 } } ], "vout": [ { "amount": 53767076642, "target": { "key": "0aaaa91b1bd9920a70ddb63a52c4b6da80d9ecfa5edc6751d020a8c9b97f36b8" } } ], "extra": [ 1, 241, 229, 139, 170, 35, 211, 129, 24, 210, 183, 125, 58, 242, 5, 225, 161, 190, 149, 244, 16, 144, 190, 46, 79, 90, 68, 77, 71, 40, 19, 139, 245, 2, 17, 0, 0, 0, 15, 23, 105, 107, 115, 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