Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d3eecd7a72057ec5c7ebc3e2ce956fb08b49601b4069df4fd247bc7ddb5f5918

Tx prefix hash: bb879714b074f5ce2220f78d798a2dd54c9a2ca93d20bdf0f283d032f7773afc
Tx public key: e27f99e87767671a4337a004bc3cedfdef3f8416e6b2f5b8a21dd9e53c89f536
Timestamp: 1629041109 Timestamp [UCT]: 2021-08-15 15:25:09 Age [y:d:h:m:s]: 04:055:21:37:55
Block: 314678 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1071497 RingCT/type: yes/0
Extra: 01e27f99e87767671a4337a004bc3cedfdef3f8416e6b2f5b8a21dd9e53c89f53602110000000c01f1e57f000000000000000000

1 output(s) for total of 55.635131626000 dcy

stealth address amount amount idx
00: fcf2bdbd863a21f8e4c75fca896b1aa8c5f5646ec3ccff2138f3966be09ec456 55.635131626000 655045 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": 314688, "vin": [ { "gen": { "height": 314678 } } ], "vout": [ { "amount": 55635131626, "target": { "key": "fcf2bdbd863a21f8e4c75fca896b1aa8c5f5646ec3ccff2138f3966be09ec456" } } ], "extra": [ 1, 226, 127, 153, 232, 119, 103, 103, 26, 67, 55, 160, 4, 188, 60, 237, 253, 239, 63, 132, 22, 230, 178, 245, 184, 162, 29, 217, 229, 60, 137, 245, 54, 2, 17, 0, 0, 0, 12, 1, 241, 229, 127, 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