Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc10bcef467a166bd6c6778b8695b3869e89a1bac7a7711b347dd301b833e318

Tx prefix hash: ba164c079e692d03a574e971f64394aeadf99aee2c09c434b408daf62b9db4f1
Tx public key: d4c75db12d3e04d04f461786da9ed526750c51e6a6ccda6ded94d37ea5ee7484
Timestamp: 1737911033 Timestamp [UCT]: 2025-01-26 17:03:53 Age [y:d:h:m:s]: 00:142:01:07:51
Block: 1205894 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101219 RingCT/type: yes/0
Extra: 01d4c75db12d3e04d04f461786da9ed526750c51e6a6ccda6ded94d37ea5ee748402110000000901491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6c2de042d0e38dcfb91280355ed8ca83f4c2a57ea74b0c8fe4c8a8c0a7b67b3f 0.600000000000 1692593 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": 1205904, "vin": [ { "gen": { "height": 1205894 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6c2de042d0e38dcfb91280355ed8ca83f4c2a57ea74b0c8fe4c8a8c0a7b67b3f" } } ], "extra": [ 1, 212, 199, 93, 177, 45, 62, 4, 208, 79, 70, 23, 134, 218, 158, 213, 38, 117, 12, 81, 230, 166, 204, 218, 109, 237, 148, 211, 126, 165, 238, 116, 132, 2, 17, 0, 0, 0, 9, 1, 73, 31, 136, 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