Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ffa256863c87971d5461e89e74c9341012d91d60dc6002fe0f56c44ed8ef222e

Tx prefix hash: d2780865591c11f7caac18da6891380dc1dd28ea88db3d28cc0bba46234c22fb
Tx public key: cc9a4baf81e2232cd0ff191d3ee64aa82c52222533c53d2e4a723511221ce9dd
Timestamp: 1601088369 Timestamp [UCT]: 2020-09-26 02:46:09 Age [y:d:h:m:s]: 04:203:08:22:07
Block: 137240 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1125431 RingCT/type: yes/0
Extra: 01cc9a4baf81e2232cd0ff191d3ee64aa82c52222533c53d2e4a723511221ce9dd0211000000108ab75de5000000000000000000

1 output(s) for total of 215.410871162000 dcy

stealth address amount amount idx
00: 29a6515029ab3f55e7b4e98194ea47be883d3adda01b14fd8f26e91a1143c2b2 215.410871162000 228309 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": 137250, "vin": [ { "gen": { "height": 137240 } } ], "vout": [ { "amount": 215410871162, "target": { "key": "29a6515029ab3f55e7b4e98194ea47be883d3adda01b14fd8f26e91a1143c2b2" } } ], "extra": [ 1, 204, 154, 75, 175, 129, 226, 35, 44, 208, 255, 25, 29, 62, 230, 74, 168, 44, 82, 34, 37, 51, 197, 61, 46, 74, 114, 53, 17, 34, 28, 233, 221, 2, 17, 0, 0, 0, 16, 138, 183, 93, 229, 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