Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e805625f8c9749f0329f4cde6538ab6c7c03ee452300fee53bedc2dbd7c8eb6f

Tx prefix hash: 67f6baa6ae968993704b84e02c729cd74cde95380c8232e1a5b4f630172023fd
Tx public key: 6b7832bc6f8f778ee9c05cf14cb76d944bf184aaf0eb71f133b31de381e01c00
Timestamp: 1715703328 Timestamp [UCT]: 2024-05-14 16:15:28 Age [y:d:h:m:s]: 00:328:15:06:33
Block: 1021934 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 234890 RingCT/type: yes/0
Extra: 016b7832bc6f8f778ee9c05cf14cb76d944bf184aaf0eb71f133b31de381e01c0002110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4ff583b874cfbf9de9f50cb249f5c63be207dea33f1607b5d113094e2bdbe531 0.600000000000 1486395 of 15

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": 1021944, "vin": [ { "gen": { "height": 1021934 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ff583b874cfbf9de9f50cb249f5c63be207dea33f1607b5d113094e2bdbe531" } } ], "extra": [ 1, 107, 120, 50, 188, 111, 143, 119, 142, 233, 192, 92, 241, 76, 183, 109, 148, 75, 241, 132, 170, 240, 235, 113, 241, 51, 179, 29, 227, 129, 224, 28, 0, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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