Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6c44fe9ecc8cd1807615ef125493269ff6ab3abd51d60b9417b4a21276decd06

Tx prefix hash: 2dfd41e313fc19827deab1f579a62db0ad235f55e65f8a92b899f2f669a4aede
Tx public key: 1119b3c0ba7c49ff027e01597ec7aee9e6b931d1ec3b5df0eda17107572dfe1f
Timestamp: 1719842546 Timestamp [UCT]: 2024-07-01 14:02:26 Age [y:d:h:m:s]: 01:136:07:22:18
Block: 1056248 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 355968 RingCT/type: yes/0
Extra: 011119b3c0ba7c49ff027e01597ec7aee9e6b931d1ec3b5df0eda17107572dfe1f021100000001ddd3db91000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1ff7fd5339bef2cb20d4632e929642d3e7ed408cffe2abb335d33a50fe175ad9 0.600000000000 1526661 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": 1056258, "vin": [ { "gen": { "height": 1056248 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1ff7fd5339bef2cb20d4632e929642d3e7ed408cffe2abb335d33a50fe175ad9" } } ], "extra": [ 1, 17, 25, 179, 192, 186, 124, 73, 255, 2, 126, 1, 89, 126, 199, 174, 233, 230, 185, 49, 209, 236, 59, 93, 240, 237, 161, 113, 7, 87, 45, 254, 31, 2, 17, 0, 0, 0, 1, 221, 211, 219, 145, 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