Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf5035faf6bed3e1d4f91b5128ca1cc02c39b12c51f188382b78d8976547ab07

Tx prefix hash: b5e0e7db2680fc3933ea36f710c990460e6a616ddeb5f390e9199b6b305cccbd
Tx public key: 295216c972be76c17f0d2380c7cccd3d7cd8d8c51adec35b3713e86d52052d85
Timestamp: 1734801702 Timestamp [UCT]: 2024-12-21 17:21:42 Age [y:d:h:m:s]: 00:093:02:50:14
Block: 1180178 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66302 RingCT/type: yes/0
Extra: 01295216c972be76c17f0d2380c7cccd3d7cd8d8c51adec35b3713e86d52052d85021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a41d48c8e135768c0b5bb6ced1e2b693afc9af178b2585334466ba7ee24b5725 0.600000000000 1666583 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": 1180188, "vin": [ { "gen": { "height": 1180178 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a41d48c8e135768c0b5bb6ced1e2b693afc9af178b2585334466ba7ee24b5725" } } ], "extra": [ 1, 41, 82, 22, 201, 114, 190, 118, 193, 127, 13, 35, 128, 199, 204, 205, 61, 124, 216, 216, 197, 26, 222, 195, 91, 55, 19, 232, 109, 82, 5, 45, 133, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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